English is not my native, but codes does not sound like a correct plural for code. Perhaps it can be replaced with something like code to be profiled

Not sure how this section is specific to ITT? User does not need to install (nor use) conda to benefit from ITT feature. Nor should it be bound to python-3.8 , as environment name suggests. And since example does not have any data dependencies, changing working directory to base folder is superfluous as well, isn't it?

But paragraph about ITT filename and folder where it will be generated are probably relevant, isn't it?

To use VTune to profile a python script, it is always recommended to wrap the execution of the python script into a bash script. Because executing a python script requires the configuration of a Python environment, which is not always there by default. Also, launching the script from vtune could be done in a directory that doesn't have the python script, so it is better to switch the active directory into the desired folder inside the bash script execution.

Detailed explanation is there in the section above:
To profile a PyTorch script, it is recommended to wrap all manual steps, including activating a Python environment and setting required environment variables, into a bash script, then profile this bash script. In the screenshot above, we wrapped all steps into the launch.sh bash script and profile bash with the parameter to be <path_of_launch.sh>.

I restated the description to make it more descriptive and related to vtune. Also I changed the specific python version and conda distribution into a generic description. Does the updated content below look good to you?

The `launch.sh` bash script, mentioned in the Intel® VTune™ Profiler GUI screenshot, to wrap all manual steps is shown below.

.. code:: bash

   # launch.sh

   #!/bin/bash

   # Retrive the directory path where the path contains both the sample.py and launch.sh so that this bash script can be invoked from any directory
   BASEFOLDER=$( cd -- "$( dirname -- "${BASH_SOURCE[0]}" )" &> /dev/null && pwd )
   <Activate a Python environment>
   cd ${BASEFOLDER}
   python sample.py

Could you please elaborate a bit more on how to read this picture? What do the big brown boxes mean? Or what does someone learn once they look at this picture?

A big convolution gets broken into multiple smaller ones on different thread?

nit : PyTorch 1.13 or later

typos : on the left side

are the three dots after "New project..." and " configure Analysis..." intended?

Yes, the three dots are shown in the VTune GUI buttons, so I copied them.

does "this" here refers to the explicit invocation?

Yes, this refers to the explicit invocation. I'll make it clear in the tutorial.

typos : In the right side `HOW --> on the right side 'How'

can you please clarify on " you can choose whatever type that you would like to profile."

Intel VTune Profiler provides a bunch of profiling types (https://www.intel.com/content/www/us/en/develop/documentation/vtune-help/top/analyze-performance.html) that users can choose from.

I wonder how the workflow works, is this correct?

1. Add context manager "with torch.autograd.profiler.emit_itt():"
2. Run the code --> it saved the traces somewhere
3. load the traces in the profiler?
   Or
   run the profiler, then With WHAT, How and Where, you can set the path of the application that you want to profile, it automatically capture the traces and show you. Assume, adding the context manager can be additional to what it does for labeling a part not the only way to capture the profiles.

This statement "you can set the path of the application that you want to profile" suggest the second path/workflow.
Can you please clarify the workflow.

It's the second way. Users launch VTune first, then launch the application from vtune. WHAT in VTune is the place to let vtune know which application to launch and profile.

You still have codes here

Again, English is not my native, but please compare results of https://www.bing.com/search?q=codes vs https://www.bing.com/search?q=code

Oh, your concern is on the plural. I'm not a native speaker as well. Changed it to code anyway. Done

@jingxu10 is it Retrieve the directory path here? Might be a typo.

Good catch. Corrected.

@jingxu10, utlized -> utilized ?

done